Animated pull-to-refresh

ABSTRACT

Aspects of the present disclosure involve a system comprising a computer-readable storage medium storing a program and method for animating a pull-to-refresh gesture. The program and method provide for receiving a pull gesture in a messaging application; selecting, in response to receiving the pull gesture, a set of users corresponding to contacts in the messaging application; and displaying a set of images for each user in the set of users, in association with refreshing screen content.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.17/371,524, filed Jul. 9, 2021, which application is a continuation ofU.S. patent application Ser. No. 16/730,363, filed Dec. 30, 2019, nowissued as U.S. Pat. No. 11,062,498, which are incorporated by referenceherein in their entireties.

TECHNICAL FIELD

The present disclosure relates generally to messaging applications,including configuring messaging applications to animate apull-to-refresh gesture.

BACKGROUND

Messaging systems provide for the exchange of message content betweenusers. For example, a messaging system allows a user to exchange messagecontent with one or more other users.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

To easily identify the discussion of any particular element or act, themost significant digit or digits in a reference number refer to thefigure number in which that element is first introduced.

FIG. 1 is a diagrammatic representation of a networked environment inwhich the present disclosure may be deployed, in accordance with someexample embodiments.

FIG. 2 is a diagrammatic representation of a messaging clientapplication, in accordance with some example embodiments.

FIG. 3 is a diagrammatic representation of a data structure asmaintained in a database, in accordance with some example embodiments.

FIG. 4 is a diagrammatic representation of a message, in accordance withsome example embodiments.

FIG. 5 is a flowchart for an access-limiting process, in accordance withsome example embodiments.

FIG. 6 is an interaction diagram illustrating a process for animating apull-to-refresh gesture, in accordance with some example embodiments.

FIG. 7 illustrates a friends feed interface with animations of userscorresponding to a pull gesture, in accordance with some exampleembodiments.

FIG. 8 illustrates a friends feed interface with animations of selectedusers corresponding to a pull gesture passing a threshold pull distance,in accordance with some example embodiments.

FIG. 9 illustrates a friends feed interface with animations of selectedusers corresponding to release of a pull gesture, in accordance withsome example embodiments.

FIG. 10 is a flowchart illustrating a process for animating apull-to-refresh gesture, in accordance with some example embodiments.

FIG. 11 is block diagram showing a software architecture within whichthe present disclosure may be implemented, in accordance with someexample embodiments.

FIG. 12 is a diagrammatic representation of a machine, in the form of acomputer system within which a set of instructions may be executed forcausing the machine to perform any one or more of the methodologiesdiscussed, in accordance with some example embodiments.

DETAILED DESCRIPTION

A messaging application typically allows users to exchange content items(e.g., messages, images and/or video) with one another in a messagethread. A messaging application may work in conjunction with a socialnetwork system which is configured to maintain the identity of users andtheir corresponding relationships (e.g., friend relationships).

In some cases, a user may wish to refresh a screen being displayed bythe messaging application. For example, the user may perform apull-to-refresh gesture on a list of users presented on the devicescreen. The pull-to-refresh gesture includes the user touching thescreen, pulling the screen downward past a threshold pull distance, andthen releasing the touch. In response to detecting the pull portion ofthe gesture, a messaging application typically provides an animationdepicting the top edge of the screen being pulled down along with thepull gesture. In response to the release portion, the messagingapplication provides an animation for the screen to move back upwards,and for display of the updated content (e.g., an updated list of users).In some cases, an end user may wish to have a more engaging experiencewith respect to refreshing screen content.

The disclosed embodiments provide for additional animations tosupplement a pull-to-refresh gesture. The messaging application displaysan animated set of friends in association with the pull-to-refreshgesture. For example, the animated set of friends is selected randomlyfrom a set of candidate friends. The candidate friends correspond tocontacts with which the end user frequently messages, and/or recentlymessaged. The set of friends are animated with different facialexpressions, accessories and/or other features relative to one another.In addition, different facial expressions, accessories and/or featuresare displayed for the friends through each stage of the pull-to-refreshgesture (e.g., the initial pull, pulling past the threshold pulldistance, and release of the pull gesture).

FIG. 1 is a block diagram showing an example messaging system 100 forexchanging data (e.g., messages and associated content) over a network.The messaging system 100 includes multiple instances of a client device102, each of which hosts a number of applications including a messagingclient application 104. Each messaging client application 104 iscommunicatively coupled to other instances of the messaging clientapplication 104 and a messaging server system 108 via a network 106(e.g., the Internet).

A messaging client application 104 is able to communicate and exchangedata with another messaging client application 104 and with themessaging server system 108 via the network 106. The data exchangedbetween the messaging client application 104, and between a messagingclient application 104 and the messaging server system 108, includesfunctions (e.g., commands to invoke functions) as well as payload data(e.g., text, audio, video or other multimedia data).

The messaging server system 108 provides server-side functionality viathe network 106 to a particular messaging client application 104. Whilecertain functions of the messaging system 100 are described herein asbeing performed by either a messaging client application 104 or by themessaging server system 108, the location of certain functionalityeither within the messaging client application 104 or the messagingserver system 108 is a design choice. For example, it may be technicallypreferable to initially deploy certain technology and functionalitywithin the messaging server system 108, but to later migrate thistechnology and functionality to the messaging client application 104where a client device 102 has a sufficient processing capacity.

The messaging server system 108 supports various services and operationsthat are provided to the messaging client application 104. Suchoperations include transmitting data to, receiving data from, andprocessing data generated by the messaging client application 104. Thisdata may include, message content, client device information,geolocation information, media annotation and overlays, message contentpersistence conditions, social network information, and live eventinformation, as examples. Data exchanges within the messaging system 100are invoked and controlled through functions available via userinterfaces (UIs) of the messaging client application 104.

Turning now specifically to the messaging server system 108, anapplication programming interface (API) server 110 is coupled to, andprovides a programmatic interface to, an application server 112. Theapplication server 112 is communicatively coupled to a database server118, which facilitates access to a database 120 in which is stored dataassociated with messages processed by the application server 112.

The API server 110 receives and transmits message data (e.g., commandsand message payloads) between the client device 102 and the applicationserver 112. Specifically, the API server 110 provides a set ofinterfaces (e.g., routines and protocols) that can be called or queriedby the messaging client application 104 in order to invoke functionalityof the application server 112. The API server 110 exposes variousfunctions supported by the application server 112, including accountregistration, login functionality, the sending of messages, via theapplication server 112, from a particular messaging client application104 to another messaging client application 104, the sending of mediafiles (e.g., images or video) from a messaging client application 104 tothe messaging server application 114, and for possible access by anothermessaging client application 104, the setting of a collection of mediadata (e.g., Story), the retrieval of a list of friends of a user of aclient device 102, the retrieval of such collections, the retrieval ofmessages and content, the adding and deletion of friends to a socialgraph, the location of friends within a social graph, and opening anapplication event (e.g., relating to the messaging client application104).

The application server 112 hosts a number of applications andsubsystems, including a messaging server application 114, an imageprocessing system 116 and a social network system 122. The messagingserver application 114 implements a number of message processingtechnologies and functions, particularly related to the aggregation andother processing of content (e.g., textual and multimedia content)included in messages received from multiple instances of the messagingclient application 104. As will be described in further detail, the textand media content from multiple sources may be aggregated intocollections of content (e.g., called Stories or galleries). Thesecollections are then made available, by the messaging server application114, to the messaging client application 104. Other processor and memoryintensive processing of data may also be performed server-side by themessaging server application 114, in view of the hardware requirementsfor such processing.

The application server 112 also includes an image processing system 116that is dedicated to performing various image processing operations,typically with respect to images or video received within the payload ofa message at the messaging server application 114.

The social network system 122 supports various social networkingfunctions services, and makes these functions and services available tothe messaging server application 114. To this end, the social networksystem 122 maintains and accesses an entity graph 304 (as shown in FIG.3 ) within the database 120. Examples of functions and servicessupported by the social network system 122 include the identification ofother users of the messaging system 100 with which a particular user hasrelationships or is “following”, and also the identification of otherentities and interests of a particular user. Such other users may bereferred to as the user's friends. In some embodiments, the socialnetwork system 122 may access location information associated with eachof the user's friends to determine where they live or are currentlylocated geographically.

FIG. 2 is block diagram illustrating further details regarding themessaging system 100, according to example embodiments. Specifically,the messaging system 100 is shown to comprise the messaging clientapplication 104 and the application server 112, which in turn embody anumber of some subsystems, namely an ephemeral timer system 202, acollection management system 204 and an annotation system 206.

The ephemeral timer system 202 is responsible for enforcing thetemporary access to content permitted by the messaging clientapplication 104 and the messaging server application 114. To this end,the ephemeral timer system 202 incorporates a number of timers that,based on duration and display parameters associated with a message, orcollection of messages (e.g., a Story), selectively display and enableaccess to messages and associated content via the messaging clientapplication 104. Further details regarding the operation of theephemeral timer system 202 are provided below.

The collection management system 204 is responsible for managingcollections of media (e.g., collections of text, image video and audiodata). In some examples, a collection of content (e.g., messages,including images, video, text and audio) may be organized into an “eventgallery” or an “event Story.” Such a collection may be made availablefor a specified time period, such as the duration of an event to whichthe content relates. For example, content relating to a music concertmay be made available as a “Story” for the duration of that musicconcert. The collection management system 204 may also be responsiblefor publishing an icon that provides notification of the existence of aparticular collection to the user interface of the messaging clientapplication 104.

The collection management system 204 furthermore includes a curationinterface 208 that allows a collection manager to manage and curate aparticular collection of content. For example, the curation interface208 enables an event organizer to curate a collection of contentrelating to a specific event (e.g., delete inappropriate content orredundant messages). Additionally, the collection management system 204employs machine vision (or image recognition technology) and contentrules to automatically curate a content collection. In certainembodiments, compensation may be paid to a user for inclusion ofuser-generated content into a collection. In such cases, the curationinterface 208 operates to automatically make payments to such users forthe use of their content.

The annotation system 206 provides various functions that enable a userto annotate or otherwise modify or edit media content associated with amessage. For example, the annotation system 206 provides functionsrelated to the generation and publishing of media overlays for messagesprocessed by the messaging system 100. The annotation system 206operatively supplies a media overlay or supplementation (e.g., an imagefilter) to the messaging client application 104 based on a geolocationof the client device 102. In another example, the annotation system 206operatively supplies a media overlay to the messaging client application104 based on other information, such as social network information ofthe user of the client device 102. A media overlay may include audio andvisual content and visual effects. Examples of audio and visual contentinclude pictures, texts, logos, animations, and sound effects. Anexample of a visual effect includes color overlaying. The audio andvisual content or the visual effects can be applied to a content item(e.g., a photo) at the client device 102. For example, the media overlaymay include text that can be overlaid on top of a photograph taken bythe client device 102. In another example, the media overlay includes anidentification of a location overlay (e.g., Venice beach), a name of alive event, or a name of a merchant overlay (e.g., Beach Coffee House).In another example, the annotation system 206 uses the geolocation ofthe client device 102 to identify a media overlay that includes the nameof a merchant at the geolocation of the client device 102. The mediaoverlay may include other indicia associated with the merchant. Themedia overlays may be stored in the database 120 and accessed throughthe database server 118.

In one example embodiment, the annotation system 206 provides auser-based publication platform that enables users to select ageolocation on a map, and upload content associated with the selectedgeolocation. The user may also specify circumstances under which aparticular media overlay should be offered to other users. Theannotation system 206 generates a media overlay that includes theuploaded content and associates the uploaded content with the selectedgeolocation.

In another example embodiment, the annotation system 206 provides amerchant-based publication platform that enables merchants to select aparticular media overlay associated with a geolocation via a biddingprocess. For example, the annotation system 206 associates the mediaoverlay of a highest bidding merchant with a corresponding geolocationfor a predefined amount of time.

FIG. 3 is a schematic diagram illustrating data structures 300 which maybe stored in the database 120 of the messaging server system 108,according to certain example embodiments. While the content of thedatabase 120 is shown to comprise a number of tables, it will beappreciated that the data could be stored in other types of datastructures (e.g., as an object-oriented database).

The database 120 includes message data stored within a message table314. The entity table 302 stores entity data, including an entity graph304. Entities for which records are maintained within the entity table302 may include individuals, corporate entities, organizations, objects,places, events, etc. Regardless of type, any entity regarding which themessaging server system 108 stores data may be a recognized entity. Eachentity is provided with a unique identifier, as well as an entity typeidentifier (not shown).

The entity graph 304 furthermore stores information regardingrelationships and associations between entities. Such relationships maybe social, professional (e.g., work at a common corporation ororganization), interested-based or activity-based, merely for example.

The database 120 also stores annotation data, in the example form offilters, in an annotation table 312. Filters for which data is storedwithin the annotation table 312 are associated with and applied tovideos (for which data is stored in a video table 310) and/or images(for which data is stored in an image table 308). Filters, in oneexample, are overlays that are displayed as overlaid on an image orvideo during presentation to a recipient user. Filters may be of variestypes, including user-selected filters from a gallery of filterspresented to a sending user by the messaging client application 104 whenthe sending user is composing a message. Other types of filters includegeolocation filters (also known as geo-filters) which may be presentedto a sending user based on geographic location. For example, geolocationfilters specific to a neighborhood or special location may be presentedwithin a user interface by the messaging client application 104, basedon geolocation information determined by a GPS unit of the client device102. Another type of filter is a data filter, which may be selectivelypresented to a sending user by the messaging client application 104,based on other inputs or information gathered by the client device 102during the message creation process. Example of data filters includecurrent temperature at a specific location, a current speed at which asending user is traveling, battery life for a client device 102, or thecurrent time.

Other annotation data that may be stored within the image table 308 isso-called “Lens” data. A “Lens” may be a real-time special effect andsound that may be added to an image or a video.

As mentioned above, the video table 310 stores video data which, in oneembodiment, is associated with messages for which records are maintainedwithin the message table 314. Similarly, the image table 308 storesimage data associated with messages for which message data is stored inthe entity table 302. The entity table 302 may associate variousannotations from the annotation table 312 with various images and videosstored in the image table 308 and the video table 310.

A story table 306 stores data regarding collections of messages andassociated image, video, or audio data, which are compiled into acollection (e.g., a Story or a gallery). The creation of a particularcollection may be initiated by a particular user (e.g., each user forwhich a record is maintained in the entity table 302). A user may createa “personal Story” in the form of a collection of content that has beencreated and sent/broadcast by that user. To this end, the user interfaceof the messaging client application 104 may include an icon that isuser-selectable to enable a sending user to add specific content to hisor her personal Story.

A collection may also constitute a “live Story,” which is a collectionof content from multiple users that is created manually, automatically,or using a combination of manual and automatic techniques. For example,a “live Story” may constitute a curated stream of user-submitted contentfrom varies locations and events. Users whose client devices havelocation services enabled and are at a common location event at aparticular time may, for example, be presented with an option, via auser interface of the messaging client application 104, to contributecontent to a particular live Story. The live Story may be identified tothe user by the messaging client application 104, based on his or herlocation. The end result is a “live Story” told from a communityperspective.

A further type of content collection is known as a “location Story”,which enables a user whose client device 102 is located within aspecific geographic location (e.g., on a college or university campus)to contribute to a particular collection. In some embodiments, acontribution to a location Story may require a second degree ofauthentication to verify that the end user belongs to a specificorganization or other entity (e.g., is a student on the universitycampus).

FIG. 4 is a schematic diagram illustrating a structure of a message 400,according to some embodiments, generated by a messaging clientapplication 104 for communication to a further messaging clientapplication 104 or the messaging server application 114. The content ofa particular message 400 is used to populate the message table 314stored within the database 120, accessible by the messaging serverapplication 114. Similarly, the content of a message 400 is stored inmemory as “in-transit” or “in-flight” data of the client device 102 orthe application server 112. The message 400 is shown to include thefollowing components:

-   -   A message identifier 402: a unique identifier that identifies        the message 400.    -   A message text payload 404: text, to be generated by a user via        a user interface of the client device 102 and that is included        in the message 400.    -   A message image payload 406: image data, captured by a camera        component of a client device 102 or retrieved from a memory        component of a client device 102, and that is included in the        message 400.    -   A message video payload 408: video data, captured by a camera        component or retrieved from a memory component of the client        device 102 and that is included in the message 400.    -   A message audio payload 410: audio data, captured by a        microphone or retrieved from a memory component of the client        device 102, and that is included in the message 400.    -   Message annotations 412: annotation data (e.g., filters,        stickers or other enhancements) that represents annotations to        be applied to message image payload 406, message video payload        408, or message audio payload 410 of the message 400.    -   A message duration parameter 414: parameter value indicating, in        seconds, the amount of time for which content of the message        (e.g., the message image payload 406, message video payload 408,        message audio payload 410) is to be presented or made accessible        to a user via the messaging client application 104.    -   A message geolocation parameter 416: geolocation data (e.g.,        latitudinal and longitudinal coordinates) associated with the        content payload of the message. Multiple message geolocation        parameter 416 values may be included in the payload, each of        these parameter values being associated with respect to content        items included in the content (e.g., a specific image within the        message image payload 406, or a specific video in the message        video payload 408).    -   A message story identifier 418: identifier values identifying        one or more content collections (e.g., “Stories”) with which a        particular content item in the message image payload 406 of the        message 400 is associated. For example, multiple images within        the message image payload 406 may each be associated with        multiple content collections using identifier values.    -   A message tag 420: each message 400 may be tagged with multiple        tags, each of which is indicative of the subject matter of        content included in the message payload. For example, where a        particular image included in the message image payload 406        depicts an animal (e.g., a lion), a tag value may be included        within the message tag 420 that is indicative of the relevant        animal. Tag values may be generated manually, based on user        input, or may be automatically generated using, for example,        image recognition.    -   A message sender identifier 422: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 102 on        which the message 400 was generated and from which the message        400 was sent.    -   A message receiver identifier 424: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 102 to        which the message 400 is addressed.

The contents (e.g., values) of the various components of message 400 maybe pointers to locations in tables within which content data values arestored. For example, an image value in the message image payload 406 maybe a pointer to (or address of) a location within an image table 308.Similarly, values within the message video payload 408 may point to datastored within a video table 310, values stored within the messageannotations 412 may point to data stored in an annotation table 312,values stored within the message story identifier 418 may point to datastored in a story table 306, and values stored within the message senderidentifier 422 and the message receiver identifier 424 may point to userrecords stored within an entity table 302.

FIG. 5 is a schematic diagram illustrating an access-limiting process500, in terms of which access to content (e.g., an ephemeral message502, and associated multimedia payload of data) or a content collection(e.g., an ephemeral message group 504) may be time-limited (e.g., madeephemeral).

An ephemeral message 502 is shown to be associated with a messageduration parameter 506, the value of which determines an amount of timethat the ephemeral message 502 will be displayed to a receiving user ofthe ephemeral message 502 by the messaging client application 104. Inone embodiment, an ephemeral message 502 is viewable by a receiving userfor up to a maximum of 10 seconds, depending on the amount of time thatthe sending user specifies using the message duration parameter 506.

The message duration parameter 506 and the message receiver identifier424 are shown to be inputs to a message timer 512, which is responsiblefor determining the amount of time that the ephemeral message 502 isshown to a particular receiving user identified by the message receiveridentifier 424. In particular, the ephemeral message 502 will only beshown to the relevant receiving user for a time period determined by thevalue of the message duration parameter 506. The message timer 512 isshown to provide output to a more generalized ephemeral timer system202, which is responsible for the overall timing of display of content(e.g., an ephemeral message 502) to a receiving user.

The ephemeral message 502 is shown in FIG. 5 to be included within anephemeral message group 504 (e.g., a collection of messages in apersonal Story, or an event Story). The ephemeral message group 504 hasan associated group duration parameter 508, a value of which determinesa time-duration for which the ephemeral message group 504 is presentedand accessible to users of the messaging system 100. The group durationparameter 508, for example, may be the duration of a music concert,where the ephemeral message group 504 is a collection of contentpertaining to that concert. Alternatively, a user (either the owninguser or a curator user) may specify the value for the group durationparameter 508 when performing the setup and creation of the ephemeralmessage group 504.

Additionally, each ephemeral message 502 within the ephemeral messagegroup 504 has an associated group participation parameter 510, a valueof which determines the duration of time for which the ephemeral message502 will be accessible within the context of the ephemeral message group504. Accordingly, a particular ephemeral message group 504 may “expire”and become inaccessible within the context of the ephemeral messagegroup 504, prior to the ephemeral message group 504 itself expiring interms of the group duration parameter 508. The group duration parameter508, group participation parameter 510, and message receiver identifier424 each provide input to a group timer 514 which operationallydetermines, firstly, whether a particular ephemeral message 502 of theephemeral message group 504 will be displayed to a particular receivinguser and, if so, for how long. Note that the ephemeral message group 504is also aware of the identity of the particular receiving user as aresult of the message receiver identifier 424.

Accordingly, the group timer 514 operationally controls the overalllifespan of an associated ephemeral message group 504, as well as anindividual ephemeral message 502 included in the ephemeral message group504. In one embodiment, each and every ephemeral message 502 within theephemeral message group 504 remains viewable and accessible for atime-period specified by the group duration parameter 508. In a furtherembodiment, a certain ephemeral message 502 may expire, within thecontext of ephemeral message group 504, based on a group participationparameter 510. Note that a message duration parameter 506 may stilldetermine the duration of time for which a particular ephemeral message502 is displayed to a receiving user, even within the context of theephemeral message group 504. Accordingly, the message duration parameter506 determines the duration of time that a particular ephemeral message502 is displayed to a receiving user, regardless of whether thereceiving user is viewing that ephemeral message 502 inside or outsidethe context of an ephemeral message group 504.

The ephemeral timer system 202 may furthermore operationally remove aparticular ephemeral message 502 from the ephemeral message group 504based on a determination that it has exceeded an associated groupparticipation parameter 510. For example, when a sending user hasestablished a group participation parameter 510 of 24 hours fromposting, the ephemeral timer system 202 will remove the relevantephemeral message 502 from the ephemeral message group 504 after thespecified 24 hours. The ephemeral timer system 202 also operates toremove an ephemeral message group 504 either when the groupparticipation parameter 510 for each and every ephemeral message 502within the ephemeral message group 504 has expired, or when theephemeral message group 504 itself has expired in terms of the groupduration parameter 508.

In certain use cases, a creator of a particular ephemeral message group504 may specify an indefinite group duration parameter 508. In thiscase, the expiration of the group participation parameter 510 for thelast remaining ephemeral message 502 within the ephemeral message group504 will determine when the ephemeral message group 504 itself expires.In this case, a new ephemeral message 502, added to the ephemeralmessage group 504, with a new group participation parameter 510,effectively extends the life of an ephemeral message group 504 to equalthe value of the group participation parameter 510.

Responsive to the ephemeral timer system 202 determining that anephemeral message group 504 has expired (e.g., is no longer accessible),the ephemeral timer system 202 communicates with the messaging system100 (and, for example, specifically the messaging client application104) to cause an indicium (e.g., an icon) associated with the relevantephemeral message group 504 to no longer be displayed within a userinterface of the messaging client application 104. Similarly, when theephemeral timer system 202 determines that the message durationparameter 506 for a particular ephemeral message 502 has expired, theephemeral timer system 202 causes the messaging client application 104to no longer display an indicium (e.g., an icon or textualidentification) associated with the ephemeral message 502.

FIG. 6 is an interaction diagram illustrating a process 600 foranimating a pull-to-refresh gesture, in accordance with some exampleembodiments. For explanatory purposes, the process 600 is primarilydescribed herein with reference to the client device 102 and themessaging server system 108. However, the process 600 is not limited tothe client device 102 and the messaging server system 108. Moreover, oneor more blocks (or operations) of the process 600 may be performed byone or more other components of the client device 102, the messagingserver system 108, and/or by other suitable devices. Further forexplanatory purposes, the blocks of the process 600 are described hereinas occurring in serial, or linearly. However, multiple blocks of theprocess 600 may occur in parallel. In addition, the blocks of theprocess 600 need not be performed in the order shown and/or one or moreblocks of the process 600 need not be performed and/or can be replacedby other operations.

As noted above, the client device 102 has an instance of the messagingclient application 104 installed thereon. The client device 102 isassociated with a respective user of the messaging server system 108,and the user is associated with a user account of the messaging serversystem 108. Further, the user is identifiable by the messaging serversystem 108 based on a unique identifier (e.g., a messaging systemidentifier, email address and/or a device identifier) associated withthe user account. In addition, the messaging server system 108implements and/or works in conjunction with a social network system 122which is configured to identify other users (e.g., friends) with whichthe user has relationships.

In the example of FIG. 6 , operations 602-608 correspond to a firstphase which relates to determining candidate friends and generatingimage sets for the candidate friends. Moreover, operations 610-624correspond to a second phase for using the image sets for a selectedsubset of the candidate friends, to provide animations in associationwith a pull-to-refresh gesture. It is understood that the second phasemay occur shortly after the first phase, or after an extended period oftime after the first phase. As such, FIG. 6 includes a dashed lineseparating the first phase and the second phase for illustrativepurposes.

A user of the messaging client application 104 may perform a usergesture (e.g., a pull-to-refresh gesture) indicating to refresh contentsfor a current screen. The messaging client application 104 has differentscreens/interfaces for which content can be refreshed in response to apull-to-refresh gesture. For example, the messaging client application104 includes a friends feed interface (e.g., discussed further belowwith respect to FIG. 7 and FIG. 8 ), a stories feed interface (notshown), and/or other types of interfaces configured to refresh inresponse to user input (e.g., a pull-to-refresh gesture).

For example, the friends feed interface includes a friends listrepresenting contacts of the user (e.g., friends) with availablemessages for viewing, status updates, and the like. The stories feedinterface includes a friends list and/or a subscription list (e.g.,publishers such as merchants, social media influencers, businesses,advertisers, and the like) representing users with available contentcollections (e.g., Stories). Each list (e.g., friends list, subscriptionlist) corresponds to a list of icons such as an image, avatar, video,emoji, label (e.g., text) and/or other representation of a respectiveuser.

Each icon may be presented with additional information (e.g., anindication of available messages for viewing, status updates for thefriends feed interface, and/or an indication of available contentcollections for the Stories feed interface). Moreover, each list isdisplayed by the messaging server system 108 according to a predefineddisplay order. Selection of a particular icon and/or the associatedadditional information within a list may provide for displaying thecontent (e.g., message, status, content collection) associatedtherewith.

As described herein, the messaging client application 104 displaysanimations (e.g., an animated set of friends) that accompany apull-to-refresh gesture, to create a more engaging interface experiencefor the user. With respect to the first phase, the messaging serversystem 108 determines candidate friends for selection (block 602). Thecandidate friends correspond to a larger group friends from which theset of friends is selected for animating.

In some embodiments, the messaging server system 108 determines thecandidate friends based on a strength of the relationship (e.g.,friendship) between the user and the contacts (e.g., friends) of theuser. For example, a stronger relationship may be determined based onthe frequency and/or recency of messages exchanged between the user andeach respective friend. Alternatively or in addition, the strength ofthe relationship may be indicated by the user (e.g., where the userspecifies closest or “best” friends within the messaging clientapplication 104). In some embodiments, the messaging server system 108is configured to limit the number of candidate friends (e.g., eightfriends), and to limit the number of friends within the set of friends(e.g., three friends). Moreover, the messaging server system 108 isconfigured to update the candidate friends on a periodic basis. In thisway, the candidate friends are based on recent data, for example, withrespect to frequency and/or recency of exchanged messages.

In some embodiments, it is possible that the number of candidate friendsis smaller than the required number for a set of friends (e.g., where agiven user has less than three total “best” friends). In such a case,the messaging client application 104 running on the client device 102may simply provide a default animation in lieu of animating a set offriends in association with the pull-to-refresh gesture.

At block 604, the messaging server system 108 determines (or generates)image sets for animating each candidate friend. Each image setcorresponds to a representation (e.g., icon, bitmoji, avatar or othertype of representation) of a candidate friend. Moreover, the image setsmay include multiple expression options (e.g., images for a happyexpression option, other images for a surprised expression option, otherimages for a neutral expression option) for animating each candidatefriend. In some embodiments, the messaging server system 108 isconfigured to generate the image sets based on a selected icon/avatarfor the friend (e.g., as selected by the friend). The messaging serversystem 108 uses preset templates and poses that can be applied to aselected icon/avatar, in order to generate the image sets for eachcandidate friend.

The messaging server system 108 provides an indication of the candidatefriends, and the image sets for animating each candidate friend, to theclient device 102 (operation 606). The client device 102 stores thereceived indication and image sets (block 608). As noted above, in someembodiments, the indication and/or image sets are updated by themessaging server system 108 (e.g., periodically). These updates are sentto the client device 102, for local storage on the client device 102.

With respect to operations 610-624 corresponding to the above-notedsecond phase, the client device 102 receives first user inputcorresponding to a pull gesture (block 610). In some embodiments, a pullgesture may correspond to an initial part of a pull-to-refresh gesture.A pull-to-refresh gesture (or swipe-to-refresh) includes touching thescreen of the client device 102 with a finger/stylus or pressing abutton on a pointing device, pulling the screen downward (or sideways,for some horizontal lists) with the finger/pointing device past athreshold pull distance, and then releasing the touch/press, as a signalto the messaging client application 104 to refresh the contents of thescreen. Thus, the pull-to-refresh gesture includes the pull gesture,followed by pulling past the threshold pull distance, and releasing thepull gesture.

At block 612, the messaging client application 104 running on the clientdevice 102 selects a set of friends from the candidate friends locallystored on the client device 102. For example, the set of friends maycorrespond to a predefined number of friends (e.g., three friends)selected from the group of candidate friends (e.g., eight friends). Insome embodiments, the selection of the set of friends is random. Assuch, the client device 102 uses a random number generator to select theset of friends from the candidate friends. Thus, in some embodiments,the set of friends corresponds to a random selection of close or “best”friends of the user.

At block 614, the messaging client application 104 running on the clientdevice 102 displays first image(s) for animating the set of friendsselected from the candidate friends. The first image(s) are included inthe set of images stored for each friend, and relates to an initialstage of a pull-to-refresh gesture. In one or more embodiments, thefirst image(s) include a set of images, for each friend, providingrespective frames displayed in sequence to provide an animation. Forexample, the first image(s) may depict an animation in which each friendin the set of friends pulls down a top edge of the screen with theirhands, so as to correspond with the pull gesture (e.g., as discussedwith respect to FIG. 7 below). Alternatively, the first image(s) mayinclude a single image for each friend (e.g., pulling down the screen),which when displayed prior to the second image(s) described below,provide for animating the set of friends.

As noted above, the set of images stored for each candidate friendincludes multiple expression options for animating the candidate friend(e.g., such that each candidate friend may be depicted with a happyfacial expression, surprised facial expression, or neutral facialexpression per animation). For each of the friends in the selected set,the client device 102 randomly selects an expression option for thatfriend. In some embodiments, for a selected set of three friends, themessaging client application 104 selects a different expression optionfor each friend. For example, the messaging client application 104selects a happy expression for the first friend, a surprised expressionfor the second friend, and a neutral expression for the third friend.

As noted above, a complete pull-to-refresh gesture requires that thepull go past a threshold pull distance. In some embodiments, the firstimage(s) include additional image(s) for depicting the set of friendswhen the messaging client application 104 detects pulling past thethreshold pull distance. For example, the additional image(s) depict aseries of images corresponding to an animation (or alternatively, asingle image) of the set of friends continuing to pull down from the topedge of the screen, but with updated facial expression (e.g., differentphases of a happy, surprised or neutral expression based on the selectedexpression option) and accessories/features (e.g., as discussed withrespect to FIG. 8 below).

At block 616, the messaging client application 104 running on the clientdevice 102 receives second user input corresponding to release of thepull gesture, thereby completing the pull-to-refresh gesture (block616). In response, the messaging client application 104 displays secondimage(s) for animating the set of friends (block 618). The secondimage(s) are included in the set of images stored for each friend, andrelate to completing the pull-to-refresh gesture. Similar to the firstimage(s), the second image(s) may correspond to a series of imagescorresponding to an animation, or a single image which when displayedafter the first image(s), provide for the animation. For example, thesecond image(s) depict the set of friends releasing the top edge of thescreen, so as to correspond with the release gesture (e.g., as discussedwith respect to FIG. 9 below).

In some embodiments, if the pull-to-refresh gesture is not completed(e.g., if the gesture does not pass the predefined threshold pulldistance and/or does not include a release), the messaging clientapplication 104 only provides for display of the appropriate firstimage(s). If the pull-to-refresh gesture is completed (e.g., the gesturepasses the predefined threshold pull distance, and includes a release),the messaging client application 104 provides for displaying the firstimage(s) and the second image(s) to animate the set of friends.

At operation 620, based on completion of the pull-to-refresh gesture,the client device 102 sends a request to refresh screen content to themessaging server system 108. In response, the messaging server system108 provides updated screen content to the client device 102 (operation622). For example, the updated screen content corresponds to an updatedlist (e.g., friends list, subscription list) within a friends feedinterface and/or a stories feed interface. At block 624, the clientdevice 102 displays the updated screen content. While FIG. 7 describesthat the messaging client application 104 running on the client device102 performs several of the operations 610-624 (e.g., corresponding tothe second phase), it is understood that these operations may instead beperformed by the messaging server system 108, such that the image setsare not stored on the client device 102.

By presenting the first image(s) and the second image(s) duringdifferent stages of the pull-to-refresh gesture, the messaging clientapplication 104 animates a randomly-selected set of friends inassociation with refreshing screen content. Such animations may providefor a more engaging interface experience for the end user.

FIGS. 7-9 illustrate an example of animating a set of friends inassociation with a pull-to-refresh gesture. More specifically, FIG. 7illustrates a friends feed interface 700 with animations of users (e.g.,friends) corresponding to the initial pull gesture, in accordance withsome example embodiments. The friends feed interface 700 includes afriends list 704 representing contacts of the user (e.g., friends). Foreach listed friend, the friends list 704 includes a name, icon (e.g.,avatar) and status for that friend. For example, the respective statusesindicate one or more of available messages for viewing, status updates,and the like. Selection of a particular icon (and/or selection of theadditional information) within the friends list 704 provides fordisplaying the content (e.g., message) or status associated with thecorresponding friend.

In addition, the messaging client application 104 in conjunction withthe messaging server system 108 provides for arranging the friends list704 according to a display order. For example, the display order isbased on a strength of the relationship (e.g., friendship) between thelisted friend and the first user. A stronger relationship is determinedbased on the frequency and/or recency of messages exchanged between thelisted friend and the first user. In another example, the strength ofthe relationship is based on a user-specified strength (e.g., where thefirst user had previously identified closest or “best” friends withinthe messaging client application 104).

The friends feed interface 700 further includes an animated set offriends 702 corresponding to the selected set of friends discussed abovewith respect to FIG. 6 . In the example of FIG. 7 , a set of threefriends is represented by respective images (e.g., bitmojis) that appearto pull down a top edge of the screen. These images are displayed, forexample, in response to the messaging client application 104 detecting apull gesture. The three friends are positioned in a row along the topedge. In some embodiments, the left, center and right positions of thethree selected users may be determined randomly by the messaging clientapplication 104.

FIG. 8 illustrates the friends feed interface 700 with animations ofselected users (e.g., friends) corresponding to a pull gesture passing athreshold pull distance, in accordance with some example embodiments. Asnoted above with respect to FIG. 6 , a pull-to-refresh gesture requiresa pull past the threshold pull distance. In response to the messagingclient application 104 detecting a pull past the threshold pulldistance, the animated set of friends 702 shown in FIG. 7 is updated inFIG. 8 to depict continued pulling down from the top edge of the screen.Moreover, the animated set of friends 702 in FIG. 8 includes differentfacial expressions and other added accessories/features (e.g., dog ears,laughter tears) relative to FIG. 7 .

FIG. 9 illustrates the friends feed interface 700 with animations ofselected users (e.g., friends) corresponding to release of a pullgesture, in accordance with some example embodiments. As noted abovewith respect to FIG. 6 , release of the pull gesture is considered tocomplete the pull-to-refresh gesture in some embodiments. In response tothe messaging client application 104 detecting a release of a pullgesture past the threshold pull distance, the animated set of friends702 shown in FIG. 8 is updated in FIG. 9 to depict that the friends havereleased the top edge of the screen. Moreover, the animated set offriends 702 in FIG. 9 includes updated facial expressions and otheradded features (e.g., showing more of the bodies of the set friends,celebratory poses for the friends, and accompanying celebratory effects)relative to FIG. 8 .

FIG. 10 is a flowchart illustrating a process 1000 for animating apull-to-refresh gesture, in accordance with some example embodiments.For explanatory purposes, the process 1000 is primarily described hereinwith reference to the client device 102 of FIG. 1 . However, one or moreblocks (or operations) of the process 1000 may be performed by one ormore other components of the client device 102, and/or by other suitabledevices. Further for explanatory purposes, the blocks of the process1000 are described herein as occurring in serial, or linearly. However,multiple blocks of the process 1000 may occur in parallel. In addition,the blocks of the process 1000 need not be performed in the order shownand/or one or more blocks of the process 1000 need not be performedand/or can be replaced by other operations.

The client device 102 receives a pull gesture in a messaging application(block 1002). The client device 102 selects, in response to receivingthe pull gesture, a set of users corresponding to contacts in themessaging application (block 1004).

The set of users may be randomly selected from among a set of candidateusers corresponding to contacts in the messaging application. The set ofcandidate users may be determined based on an amount of engagement witheach user within the set of candidate users.

The client device 102 displays a set of images for each user in the setof users, in association with refreshing screen content (block 1006).The set of images may include a respective animation for each of theusers. The set of images may include a respective bitmoji for each ofthe users.

The client device 102 may receive a release of the pull gesture. Inresponse to receiving the release of the pull gesture, the client device102 may provide a request for refreshing the screen content. In responseto providing the request, the client device 102 may receive updatedscreen content for displaying in association with the set of images.

Providing the request may be further in response to detecting athreshold pull distance for the pull gesture. For each user in the setof users, a different image may be displayed with respect to initiatingthe pull gesture, pulling past the threshold pull distance, andreleasing the pull gesture.

FIG. 11 is a block diagram 1100 illustrating a software architecture1104, which can be installed on any one or more of the devices describedherein. The software architecture 1104 is supported by hardware such asa machine 1102 that includes processors 1120, memory 1126, and I/Ocomponents 1138. In this example, the software architecture 1104 can beconceptualized as a stack of layers, where each layer provides aparticular functionality. The software architecture 1104 includes layerssuch as an operating system 1112, libraries 1110, frameworks 1108, andapplications 1106. Operationally, the applications 1106 invoke API calls1150 through the software stack and receive messages 1152 in response tothe API calls 1150.

The operating system 1112 manages hardware resources and provides commonservices. The operating system 1112 includes, for example, a kernel1114, services 1116, and drivers 1122. The kernel 1114 acts as anabstraction layer between the hardware and the other software layers.For example, the kernel 1114 provides memory management, processormanagement (e.g., scheduling), component management, networking, andsecurity settings, among other functionality. The services 1116 canprovide other common services for the other software layers. The drivers1122 are responsible for controlling or interfacing with the underlyinghardware. For instance, the drivers 1122 can include display drivers,camera drivers, BLUETOOTH® or BLUETOOTH® Low Energy drivers, flashmemory drivers, serial communication drivers (e.g., Universal Serial Bus(USB) drivers), WI-FI® drivers, audio drivers, power management drivers,and so forth.

The libraries 1110 provide a low-level common infrastructure used by theapplications 1106. The libraries 1110 can include system libraries 1118(e.g., C standard library) that provide functions such as memoryallocation functions, string manipulation functions, mathematicfunctions, and the like. In addition, the libraries 1110 can include APIlibraries 1124 such as media libraries (e.g., libraries to supportpresentation and manipulation of various media formats such as MovingPicture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC),Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC),Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group(JPEG or JPG), or Portable Network Graphics (PNG)), graphics libraries(e.g., an OpenGL framework used to render in two dimensions (2D) andthree dimensions (3D) in a graphic content on a display), databaselibraries (e.g., SQLite to provide various relational databasefunctions), web libraries (e.g., WebKit to provide web browsingfunctionality), and the like. The libraries 1110 can also include a widevariety of other libraries 1128 to provide many other APIs to theapplications 1106.

The frameworks 1108 provide a high-level common infrastructure that isused by the applications 1106. For example, the frameworks 1108 providevarious graphical user interface (GUI) functions, high-level resourcemanagement, and high-level location services. The frameworks 1108 canprovide a broad spectrum of other APIs that can be used by theapplications 1106, some of which may be specific to a particularoperating system or platform.

In an example embodiment, the applications 1106 may include a homeapplication 1136, a contacts application 1130, a browser application1132, a book reader application 1134, a location application 1142, amedia application 1144, a messaging application 1146 (e.g.,corresponding to the messaging client application 104), a gameapplication 1148, and a broad assortment of other applications such asthird-party applications 1140. The applications 1106 are programs thatexecute functions defined in the programs. Various programming languagescan be employed to create one or more of the applications 1106,structured in a variety of manners, such as object-oriented programminglanguages (e.g., Objective-C, Java, or C++) or procedural programminglanguages (e.g., C or assembly language). In a specific example, thethird-party applications 1140 (e.g., applications developed using theANDROID™ or IOS™ software development kit (SDK) by an entity other thanthe vendor of the particular platform) may be mobile software running ona mobile operating system such as IOS™, ANDROID™ WINDOWS® Phone, oranother mobile operating system. In this example, the third-partyapplications 1140 can invoke the API calls 1150 provided by theoperating system 1112 to facilitate functionality described herein.

FIG. 12 is a diagrammatic representation of a machine 1200 within whichinstructions 1208 (e.g., software, a program, an application, an applet,an app, or other executable code) for causing the machine 1200 toperform any one or more of the methodologies discussed herein may beexecuted. For example, the instructions 1208 may cause the machine 1200to execute any one or more of the methods described herein. Theinstructions 1208 transform the general, non-programmed machine 1200into a particular machine 1200 programmed to carry out the described andillustrated functions in the manner described. The machine 1200 mayoperate as a standalone device or may be coupled (e.g., networked) toother machines. In a networked deployment, the machine 1200 may operatein the capacity of a server machine or a client machine in aserver-client network environment, or as a peer machine in apeer-to-peer (or distributed) network environment. The machine 1200 maycomprise, but not be limited to, a server computer, a client computer, apersonal computer (PC), a tablet computer, a laptop computer, a netbook,a set-top box (STB), a PDA, an entertainment media system, a cellulartelephone, a smart phone, a mobile device, a wearable device (e.g., asmart watch), a smart home device (e.g., a smart appliance), other smartdevices, a web appliance, a network router, a network switch, a networkbridge, or any machine capable of executing the instructions 1208,sequentially or otherwise, that specify actions to be taken by themachine 1200. Further, while only a single machine 1200 is illustrated,the term “machine” shall also be taken to include a collection ofmachines that individually or jointly execute the instructions 1208 toperform any one or more of the methodologies discussed herein.

The machine 1200 may include processors 1202, memory 1204, and I/Ocomponents 1244, which may be configured to communicate with each othervia a bus 1242. In an example embodiment, the processors 1202 (e.g., aCentral Processing Unit (CPU), a Reduced Instruction Set Computing(RISC) processor, a Complex Instruction Set Computing (CISC) processor,a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), anASIC, a Radio-Frequency Integrated Circuit (RFIC), another processor, orany suitable combination thereof) may include, for example, a processor1206 and a processor 1210 that execute the instructions 1208. The term“processor” is intended to include multi-core processors that maycomprise two or more independent processors (sometimes referred to as“cores”) that may execute instructions contemporaneously. Although FIG.12 shows multiple processors 1202, the machine 1200 may include a singleprocessor with a single core, a single processor with multiple cores(e.g., a multi-core processor), multiple processors with a single core,multiple processors with multiples cores, or any combination thereof.

The memory 1204 includes a main memory 1212, a static memory 1214, and astorage unit 1216, both accessible to the processors 1202 via the bus1242. The main memory 1204, the static memory 1214, and storage unit1216 store the instructions 1208 embodying any one or more of themethodologies or functions described herein. The instructions 1208 mayalso reside, completely or partially, within the main memory 1212,within the static memory 1214, within machine-readable medium 1218within the storage unit 1216, within at least one of the processors 1202(e.g., within the processor's cache memory), or any suitable combinationthereof, during execution thereof by the machine 1200.

The I/O components 1244 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 1244 that are included in a particular machine will depend onthe type of machine. For example, portable machines such as mobilephones may include a touch input device or other such input mechanisms,while a headless server machine will likely not include such a touchinput device. It will be appreciated that the I/O components 1244 mayinclude many other components that are not shown in FIG. 12 . In variousexample embodiments, the I/O components 1244 may include outputcomponents 1228 and input components 1230. The output components 1228may include visual components (e.g., a display such as a plasma displaypanel (PDP), a light emitting diode (LED) display, a liquid crystaldisplay (LCD), a projector, or a cathode ray tube (CRT)), acousticcomponents (e.g., speakers), haptic components (e.g., a vibratory motor,resistance mechanisms), other signal generators, and so forth. The inputcomponents 1230 may include alphanumeric input components (e.g., akeyboard, a touch screen configured to receive alphanumeric input, aphoto-optical keyboard, or other alphanumeric input components),point-based input components (e.g., a mouse, a touchpad, a trackball, ajoystick, a motion sensor, or another pointing instrument), tactileinput components (e.g., a physical button, a touch screen that provideslocation and/or force of touches or touch gestures, or other tactileinput components), audio input components (e.g., a microphone), and thelike.

In further example embodiments, the I/O components 1244 may includebiometric components 1232, motion components 1234, environmentalcomponents 1236, or position components 1238, among a wide array ofother components. For example, the biometric components 1232 includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram-basedidentification), and the like. The motion components 1234 includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environmental components 1236 include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometers that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensors (e.g., gasdetection sensors to detection concentrations of hazardous gases forsafety or to measure pollutants in the atmosphere), or other componentsthat may provide indications, measurements, or signals corresponding toa surrounding physical environment. The position components 1238 includelocation sensor components (e.g., a GPS receiver component), altitudesensor components (e.g., altimeters or barometers that detect airpressure from which altitude may be derived), orientation sensorcomponents (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 1244 further include communication components 1240operable to couple the machine 1200 to a network 1220 or devices 1222via a coupling 1226 and a coupling 1224, respectively. For example, thecommunication components 1240 may include a network interface componentor another suitable device to interface with the network 1220. Infurther examples, the communication components 1240 may include wiredcommunication components, wireless communication components, cellularcommunication components, Near Field Communication (NFC) components,Bluetooth© components (e.g., Bluetooth® Low Energy), Wi-Fi© components,and other communication components to provide communication via othermodalities. The devices 1222 may be another machine or any of a widevariety of peripheral devices (e.g., a peripheral device coupled via aUSB).

Moreover, the communication components 1240 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 1240 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components1240, such as location via Internet Protocol (IP) geolocation, locationvia Wi-Fi® signal triangulation, location via detecting an NFC beaconsignal that may indicate a particular location, and so forth.

The various memories (e.g., memory 1204, main memory 1212, static memory1214, and/or memory of the processors 1202) and/or storage unit 1216 maystore one or more sets of instructions and data structures (e.g.,software) embodying or used by any one or more of the methodologies orfunctions described herein. These instructions (e.g., the instructions1208), when executed by processors 1202, cause various operations toimplement the disclosed embodiments.

The instructions 1208 may be transmitted or received over the network1220, using a transmission medium, via a network interface device (e.g.,a network interface component included in the communication components1240) and using any one of a number of well-known transfer protocols(e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions1208 may be transmitted or received using a transmission medium via thecoupling 1224 (e.g., a peer-to-peer coupling) to the devices 1222.

A “carrier signal” refers to any intangible medium that is capable ofstoring, encoding, or carrying instructions for execution by themachine, and includes digital or analog communications signals or otherintangible media to facilitate communication of such instructions.Instructions may be transmitted or received over a network using atransmission medium via a network interface device.

A “client device” refers to any machine that interfaces to acommunications network to obtain resources from one or more serversystems or other client devices. A client device may be, but is notlimited to, a mobile phone, desktop computer, laptop, portable digitalassistants (PDAs), smartphones, tablets, ultrabooks, netbooks, laptops,multi-processor systems, microprocessor-based or programmable consumerelectronics, game consoles, set-top boxes, or any other communicationdevice that a user may use to access a network.

A “communication network” refers to one or more portions of a networkthat may be an ad hoc network, an intranet, an extranet, a virtualprivate network (VPN), a local area network (LAN), a wireless LAN(WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitanarea network (MAN), the Internet, a portion of the Internet, a portionof the Public Switched Telephone Network (PSTN), a plain old telephoneservice (POTS) network, a cellular telephone network, a wirelessnetwork, a Wi-Fi® network, another type of network, or a combination oftwo or more such networks. For example, a network or a portion of anetwork may include a wireless or cellular network and the coupling maybe a Code Division Multiple Access (CDMA) connection, a Global Systemfor Mobile communications (GSM) connection, or other types of cellularor wireless coupling. In this example, the coupling may implement any ofa variety of types of data transfer technology, such as Single CarrierRadio Transmission Technology (1×RTT), Evolution-Data Optimized (EVDO)technology, General Packet Radio Service (GPRS) technology, EnhancedData rates for GSM Evolution (EDGE) technology, third GenerationPartnership Project (3GPP) including 3G, fourth generation wireless (4G)networks, Universal Mobile Telecommunications System (UMTS), High SpeedPacket Access (HSPA), Worldwide Interoperability for Microwave Access(WiMAX), Long Term Evolution (LTE) standard, others defined by variousstandard-setting organizations, other long-range protocols, or otherdata transfer technology.

A “component” refers to a device, physical entity, or logic havingboundaries defined by function or subroutine calls, branch points, APIs,or other technologies that provide for the partitioning ormodularization of particular processing or control functions. Componentsmay be combined via their interfaces with other components to carry outa machine process. A component may be a packaged functional hardwareunit designed for use with other components and a part of a program thatusually performs a particular function of related functions. Componentsmay constitute either software components (e.g., code embodied on amachine-readable medium) or hardware components. A “hardware component”is a tangible unit capable of performing certain operations and may beconfigured or arranged in a certain physical manner. In various exampleembodiments, one or more computer systems (e.g., a standalone computersystem, a client computer system, or a server computer system) or one ormore hardware components of a computer system (e.g., a processor or agroup of processors) may be configured by software (e.g., an applicationor application portion) as a hardware component that operates to performcertain operations as described herein. A hardware component may also beimplemented mechanically, electronically, or any suitable combinationthereof. For example, a hardware component may include dedicatedcircuitry or logic that is permanently configured to perform certainoperations. A hardware component may be a special-purpose processor,such as a field-programmable gate array (FPGA) or an applicationspecific integrated circuit (ASIC). A hardware component may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. For example, a hardwarecomponent may include software executed by a general-purpose processoror other programmable processor. Once configured by such software,hardware components become specific machines (or specific components ofa machine) uniquely tailored to perform the configured functions and areno longer general-purpose processors. It will be appreciated that thedecision to implement a hardware component mechanically, in dedicatedand permanently configured circuitry, or in temporarily configuredcircuitry (e.g., configured by software), may be driven by cost and timeconsiderations. Accordingly, the phrase “hardware component” (or“hardware-implemented component”) should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner or to perform certainoperations described herein. Considering embodiments in which hardwarecomponents are temporarily configured (e.g., programmed), each of thehardware components need not be configured or instantiated at any oneinstance in time. For example, where a hardware component comprises ageneral-purpose processor configured by software to become aspecial-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware components) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware component at one instanceof time and to constitute a different hardware component at a differentinstance of time. Hardware components can provide information to, andreceive information from, other hardware components. Accordingly, thedescribed hardware components may be regarded as being communicativelycoupled. Where multiple hardware components exist contemporaneously,communications may be achieved through signal transmission (e.g., overappropriate circuits and buses) between or among two or more of thehardware components. In embodiments in which multiple hardwarecomponents are configured or instantiated at different times,communications between such hardware components may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware components have access. Forexample, one hardware component may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware component may then, at alater time, access the memory device to retrieve and process the storedoutput. Hardware components may also initiate communications with inputor output devices, and can operate on a resource (e.g., a collection ofinformation). The various operations of example methods described hereinmay be performed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implementedcomponents that operate to perform one or more operations or functionsdescribed herein. As used herein, “processor-implemented component”refers to a hardware component implemented using one or more processors.Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors orprocessor-implemented components. Moreover, the one or more processorsmay also operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an API). The performance ofcertain of the operations may be distributed among the processors, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processors orprocessor-implemented components may be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other example embodiments, the processors orprocessor-implemented components may be distributed across a number ofgeographic locations.

A “computer-readable medium” refers to both machine-storage media andtransmission media. Thus, the terms include both storage devices/mediaand carrier waves/modulated data signals. The terms “machine-readablemedium,” “computer-readable medium” and “device-readable medium” meanthe same thing and may be used interchangeably in this disclosure.

An “ephemeral message” refers to a message that is accessible for atime-limited duration. An ephemeral message may be a text, an image, avideo and the like. The access time for the ephemeral message may be setby the message sender. Alternatively, the access time may be a defaultsetting or a setting specified by the recipient. Regardless of thesetting technique, the message is transitory.

A “machine-storage medium” refers to a single or multiple storagedevices and/or media (e.g., a centralized or distributed database,and/or associated caches and servers) that store executableinstructions, routines and/or data. The term shall accordingly be takento include, but not be limited to, solid-state memories, and optical andmagnetic media, including memory internal or external to processors.Specific examples of machine-storage media, computer-storage mediaand/or device-storage media include non-volatile memory, including byway of example semiconductor memory devices, e.g., erasable programmableread-only memory (EPROM), electrically erasable programmable read-onlymemory (EEPROM), FPGA, and flash memory devices; magnetic disks such asinternal hard disks and removable disks; magneto-optical disks; andCD-ROM and DVD-ROM disks The terms “machine-storage medium,”“device-storage medium,” “computer-storage medium” mean the same thingand may be used interchangeably in this disclosure. The terms“machine-storage media,” “computer-storage media,” and “device-storagemedia” specifically exclude carrier waves, modulated data signals, andother such media, at least some of which are covered under the term“signal medium.”

A “processor” refers to any circuit or virtual circuit (a physicalcircuit emulated by logic executing on an actual processor) thatmanipulates data values according to control signals (e.g., “commands”,“op codes”, “machine code”, etc.) and which produces correspondingoutput signals that are applied to operate a machine. A processor may,for example, be a Central Processing Unit (CPU), a Reduced InstructionSet Computing (RISC) processor, a Complex Instruction Set Computing(CISC) processor, a Graphics Processing Unit (GPU), a Digital SignalProcessor (DSP), an Application Specific Integrated Circuit (ASIC), aRadio-Frequency Integrated Circuit (RFIC) or any combination thereof. Aprocessor may further be a multi-core processor having two or moreindependent processors (sometimes referred to as “cores”) that mayexecute instructions contemporaneously.

A “signal medium” refers to any intangible medium that is capable ofstoring, encoding, or carrying the instructions for execution by amachine and includes digital or analog communications signals or otherintangible media to facilitate communication of software or data. Theterm “signal medium” shall be taken to include any form of a modulateddata signal, carrier wave, and so forth. The term “modulated datasignal” means a signal that has one or more of its characteristics setor changed in such a matter as to encode information in the signal. Theterms “transmission medium” and “signal medium” mean the same thing andmay be used interchangeably in this disclosure.

Changes and modifications may be made to the disclosed embodimentswithout departing from the scope of the present disclosure. These andother changes or modifications are intended to be included within thescope of the present disclosure, as expressed in the following claims.

What is claimed is:
 1. A method, comprising: receiving a predefinedgesture in association with an edge displayed on a screen; selecting, inresponse to receiving the predefined gesture, a set of userscorresponding to user contacts; and displaying an animation of the setof users pulling the edge across the screen.
 2. The method of claim 1,receiving a release of the predefined gesture; providing, in response toreceiving the release of the predefined gesture, a request forrefreshing screen content in association with displaying the animation;and receiving, in response to providing the request, updated screencontent for displaying in association with the animation.
 3. The methodof claim 2, wherein providing the request is further in response todetecting a threshold pull distance for the predefined gesture.
 4. Themethod of claim 3, wherein for each user in the set of users a differentimage is displayed with respect to initiating the predefined gesture,pulling past the threshold pull distance, and releasing the predefinedgesture.
 5. The method of claim 1, wherein the animation comprises arespective animation for each user in the set of users, and wherein theanimation comprises a respective bitmoji for each user in the set ofusers.
 6. The method of claim 1, wherein the predefined gesture is aswipe gesture.
 7. The method of claim 1, wherein the set of users israndomly selected from among a set of candidate users corresponding touser contacts.
 8. The method of claim 7, wherein the set of candidateusers is determined based on an amount of engagement with each userwithin the set of candidate users.
 9. A device comprising: at least oneprocessor; and a memory storing instructions that, when executed by theat least one processor, configure the at least one processor to performoperations comprising: receiving a predefined gesture in associationwith an edge displayed on a screen; selecting, in response to receivingthe predefined gesture, a set of users corresponding to user contacts;and displaying an animation of the set of users pulling the edge acrossthe screen.
 10. The device of claim 9, the operations furthercomprising: receiving a release of the predefined gesture; providing, inresponse to receiving the release of the predefined gesture, a requestfor refreshing screen content in association with displaying theanimation; and receiving, in response to providing the request, updatedscreen content for displaying in association with the animation.
 11. Thedevice of claim 10, wherein providing the request is further in responseto detecting a threshold pull distance for the predefined gesture. 12.The device of claim 11, wherein for each user in the set of users, adifferent image is displayed with respect to initiating the predefinedgesture, pulling past the threshold pull distance, and releasing thepredefined gesture.
 13. The device of claim 9, wherein the animationcomprises a respective animation for each user in the set of users, andwherein the animation comprises a respective bitmoji for each user inthe set of users.
 14. The device of claim 9, wherein the predefinedgesture is a swipe gesture.
 15. The device of claim 9, wherein the setof users is randomly selected from among a set of candidate userscorresponding to user contacts.
 16. The device of claim 15, wherein theset of candidate users is determined based on an amount of engagementwith each user within the set of candidate users.
 17. A non-transitorycomputer-readable storage medium, the computer-readable storage mediumincluding instructions that when executed by a computer, cause thecomputer to perform operations comprising: receiving a predefinedgesture in association with an edge displayed on a screen; selecting, inresponse to receiving the predefined gesture, a set of userscorresponding to user contacts; and displaying an animation of the setof users pulling the edge across the screen.
 18. The computer-readablestorage medium of claim 17, the operations further comprising: receivinga release of the predefined gesture; providing, in response to receivingthe release of the predefined gesture, a request for refreshing screencontent in association with displaying the animation; and receiving, inresponse to providing the request, updated screen content for displayingin association with the animation.
 19. The computer-readable storagemedium of claim 18, wherein providing the request is further in responseto detecting a threshold pull distance for the predefined gesture. 20.The computer-readable storage medium of claim 19, wherein for each userin the set of users, a different image is displayed with respect toinitiating the predefined gesture, pulling past the threshold pulldistance, and releasing the predefined gesture.